home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980901-19981211
/
000001_news@newsmaster….columbia.edu _Tue Sep 1 18:10:13 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id SAA24201
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 1 Sep 1998 18:10:13 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id SAA10615
for kermit.misc@watsun; Tue, 1 Sep 1998 18:10:13 -0400 (EDT)
Path: news.columbia.edu!panix!howland.erols.net!vixen.cso.uiuc.edu!news.indiana.edu!not-for-mail
From: jsue@cs.indiana.edu (jeff l sue)
Newsgroups: comp.os.vms,comp.protocols.kermit.misc
Subject: Re: How I implemented an application using C-Kermit for VMS
Date: 1 Sep 1998 22:08:43 GMT
Organization: NOT!
Lines: 36
Message-ID: <6shr9b$qsq$1@jetsam.uits.indiana.edu>
References: <6s1kq5$65p$1@client3.news.psi.net> <6sfhis$4hi$1@jetsam.uits.indiana.edu> <6sh08l$1dv$1@apakabar.cc.columbia.edu>
NNTP-Posting-Host: sheepskin.cs.indiana.edu
X-Newsreader: trn 4.0-test66 (4 June 1998)
Xref: news.columbia.edu comp.os.vms:185148 comp.protocols.kermit.misc:9158
In article <6sh08l$1dv$1@apakabar.cc.columbia.edu>,
Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
>In article <6sfhis$4hi$1@jetsam.uits.indiana.edu>,
>jeff l sue <jsue@cs.indiana.edu> wrote:
>: In article <6s1kq5$65p$1@client3.news.psi.net>,
>: Bob Kennedy <bkennedy@peco-energy.com> wrote:
>: >
>That's the good thing about alpha paging. TAP is a protocol that lets the
>page sender know whether the page was delivered successfully -- at least to
>the paging service. Of course it is the paging service's responsibility
>to deliver it to the pager. And of course it is also the responsibility of
>the person carrying the page to read the page promptly and respond to it,
>but that's somewhat beyond software control.
>
Right, but my comments address the latter part of your paragraph: Something
needs to insure that the receiver actually got the message. There are many
different reasons that the page may not make it. For example (real world
experience): Pager accidentally turned off (by children), pager lost,
battery died, on airplane when page happened, inept/unwilling receiver, etc.
The C-Kermit solution can be used to send the page, but some other complexity
needs to be added to the paging application that provides for positive
confirmation from the receiver that the page got through. If that confirmation
doesn't arrive within x-minutes, then escalate one level - which may mean just
trying again to the same pager. Wait x-more minutes, then escalate to level2,
etc. At some point, upper management should be in the escalation process.
Without this, the effort spent on the paging application could result in
messages going into the bit-bucket.
--
JLS -- *I* said that - since I can | Help stamp out abolitionists!
barely speak for myself, don't |
even think of blaming someone | Ignorance is bliss...
else. | for awhile anyway...